5.3.3 APPX Application Design Manual

+ Chapter 1-1: Overview of Application Design
+ Chapter 1-2: Getting Started
- Chapter 1-3: Data Dictionary
+ Chapter 1-4: Understanding Process Design
+ Chapter 1-5: Interprocess Communication
+ Chapter 1-6: Customizing Your Application
+ Chapter 1-7: The Documentation Facility
+ Chapter 1-8: Application Design Tools
+ Chapter 2-1: Data Dictionary Overview
+ Chapter 2-2: Data Dictionary Concepts
+ Chapter 2-3: Domains
+ Chapter 2-4: Files and Fields
+ Chapter 2-5: Work Fields
+ Chapter 3-1: Overview of APPX Processes
+ Chapter 3-2: Getting Started
+ Chapter 3-3: Process Definition
+ Chapter 3-4: Menu Processes
+ Chapter 3-5: Job Processes
+ Chapter 3-6: Input Processes
+ Chapter 3-7: Output Processes
+ Chapter 3-8: Update Processes
+ Chapter 3-9: Query Processes
+ Chapter 3-10: Inquiry Processes
+ Chapter 3-11: Status Processes
+ Chapter 3-12: Subroutine Processes
+ Chapter 3-13: Table Processes
+ Chapter 3-14: Automatic and Optional Children
+ Chapter 3-15: Using the Image Editor
+ Chapter 3-16: Using GUI Features of the Image Editor
+ Chapter 3-17: Using Event Points
+ Chapter 4-1: ILF Integration
+ Chapter 4-2: True/False Status Indicators
+ Chapter 4-3: Specifying Statements
+ Chapter 4-4: The ILF Editor
+ Chapter 4-5: The Appx ILF Debugger
+ Chapter 4-6: ILF Keyword Reference
+ Chapter 4-7: Predefined Fields
+ Chapter 4-8: Runtime Subroutine's and Predefined Processes
+ Chapter 4-9: Appx Chart Director API

Chapter 1-3: Data Dictionary

Record Protection Fields


Record protection fields instruct APPX to verify whether or not a user is allowed to delete a record or change a primary key value in a record. Use of these fields allows you to maintain referential integrity within an application.

Delete Protection fields govern whether or not a user can delete a record while executing an input process. These fields can be used to prevent the creation of 'Orphan' records, by prohibiting the deletion of any record that is referenced by other records in the application.

Key Protection fields govern whether or not a user can modify the primary key to a record while executing an input process. These fields can be used to prohibit modification of primary keys that are referenced by other records, thus also preventing 'orphan' records.

Record Access fields contain designer-designated security codes that automatically restrict the ability to retrieve a record (and by implication any field on the record) to users with security profiles that include this code. If a user does not have access to the record, APPX responds as if the record is not on file. The designer must maintain the values in this type of field.

Application Design Manual                                         "Powered by Appx Software"

59

©2006 By APPX Software, Inc. All Rights Reserved